Routing based on detected stops

ABSTRACT

In some implementations, a computing device receives a start location and a destination location, determines routes between the start location and the destination location, identifies stop signs and stop lights along the determined routes, determines delays attributable to stop signs or stop lights along the determined routes, determines travel times for routes based on the delays attributable to stop signs or stop lights along the determined routes, and presents a suggested departure time determined based on the stop sign and stop light information.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation of and claims priority to U.S. patentapplication Ser. No. 15/010,476, entitled “Routing Based on DetectedStops,” filed on Jan. 29, 2016, which is a continuation of and claimspriority to U.S. patent application Ser. No. 14/338,265, entitled“Routing Based on Detected Stops,” filed Jul. 22, 2014, which is acontinuation of and claims priority to U.S. patent application Ser. No.13/669,934, entitled “Routing Based on Detected Stops,” filed Nov. 6,2012, the entire contents of which are both incorporated herein byreference.

TECHNICAL FIELD

The disclosure generally relates to navigation and routing.

BACKGROUND

Modern mobile devices often include navigational hardware and softwareto aid users when travelling from one location to another. A user caninput a destination and the mobile device can present one or more routesfrom a start location to a destination location. Often route informationwill include the distance from the start location to the destinationlocation. Sometimes the route information will include an estimate ofthe amount of time that it will take to travel from the current locationto the destination location based on distance and speed. The user mayselect which route to take based on the distance or estimated time.However, the estimated time may be inaccurate due to traffic conditionsthat may not be known and/or included in the time estimate.

SUMMARY

In some implementations, a mobile device can transmit trafficinformation to a server for analysis. The traffic information caninclude movement information including detected stops and durations ofdetected stops. The traffic information can be analyzed to detecttraffic patterns that indicate locations of stop signs and/or stoplights. The traffic information can be analyzed to determine durationsof stops at stop signs and/or stop lights. The durations of stops can beassociated with a time of day and/or day of the week. In someimplementations, navigational routes can be determined based stop signand/or stop light information, including the delays attributable todetected stop signs and/or stop lights.

Particular implementations provide at least the following advantages:More accurate travel time estimates can be calculated when stopsign/stop light information is included in route determinations. Betteror faster routes can be determined when stop sign/stop light informationis included in the route determination. A best time to travel to avoidstops can be determined using stop sign/stop light information.

Details of one or more implementations are set forth in the accompanyingdrawings and the description below. Other features, aspects, andpotential advantages will be apparent from the description and drawings,and from the claims.

DESCRIPTION OF DRAWINGS

FIG. 1 is an example system for collecting and analyzing trafficinformation.

FIG. 2 is an illustration of traffic patterns associated with a stopsign.

FIG. 3 is an illustration of traffic patterns associated with a stoplight.

FIG. 4 is an example graphical user interface for presenting stopsign/stop light information.

FIG. 5 is an example user interface for receiving routing parameters.

FIG. 6A is flow diagram of an example process for stop sign/stop lightdetermination.

FIG. 6B is a flow diagram of an example process for displaying stopsign/stop light information.

FIG. 6C is a flow diagram of an example process for route determinationbased on stop sign/stop light information.

FIG. 7 is a block diagram of an exemplary system architectureimplementing the features and processes of FIGS. 1-6C.

Like reference symbols in the various drawings indicate like elements.

DETAILED DESCRIPTION

This disclosure describes various Graphical User Interfaces (GUIs) forimplementing various features, processes or workflows. These GUIs can bepresented on a variety of electronic devices including but not limitedto laptop computers, desktop computers, computer terminals, televisionsystems, tablet computers, e-book readers and smart phones. One or moreof these electronic devices can include a touch-sensitive surface. Thetouch-sensitive surface can process multiple simultaneous points ofinput, including processing data related to the pressure, degree orposition of each point of input. Such processing can facilitate gestureswith multiple fingers, including pinching and swiping.

When the disclosure refers to “select” or “selecting” user interfaceelements in a GUI, these terms are understood to include clicking or“hovering” with a mouse or other input device over a user interfaceelement, or touching, tapping or gesturing with one or more fingers orstylus on a user interface element. User interface elements can bevirtual buttons, menus, selectors, switches, sliders, scrubbers, knobs,thumbnails, links, icons, radial buttons, checkboxes and any othermechanism for receiving input from, or providing feedback to a user.

Collecting Traffic Information

FIG. 1 is an example system 100 for collecting and analyzing trafficinformation. In some implementations, system 100 can include mobiledevice 102 and/or mobile device 104. For example, mobile device 104 canhave similar capabilities as mobile device 102, described below.

In some implementations, mobile device 102 can include sensors, softwareand/or hardware for determining or tracking the location of mobiledevice 102. For example, mobile device 102 can include a globalnavigation satellite system (GNSS) receiver for determining the locationof mobile device 102. Mobile device 102 can receive satellite signalsfrom one or more GNSS satellites 106 and determine the location ofmobile device 102 based on the satellite signals according to knownmethods. Mobile device 102 can include cellular and/or WiFi transceiversfor receiving and transmitting cellular and/or WiFi signals. Thecellular and/or WiFi signals can be used to determine a location formobile device 102 based on known locations for the cellular or WiFitransmitters 108 that are transmitting the cellular or WiFi signals. Forexample, mobile device 102 can use triangulation or location averagingto determine the location of mobile device 102 based on the cellularand/or WiFi signals.

In some implementations, mobile device can be configured with motionsensors to determine when mobile device 102 is moving or stopped. Forexample, mobile device 102 can be configured with an accelerometer, agyroscope or any other motion sensor capable of detecting the movementof mobile device 102.

In some implementations, mobile device 102 can be configured todetermine and track the location of mobile device 102 as mobile device102 moves. For example, if mobile device 102 is in a moving vehicle,mobile device 102 can track the location of the vehicle as the vehiclemoves. The location information (i.e., traffic information) can includeGNSS data and/or motion sensor data. For example, the motion sensor datacan be used to determine when mobile device 102 is moving or stopped.The motion sensor data along with the mobile device's internal clock canbe used to determine how long (e.g., duration) the mobile device ismoving or stopped. The sensor data can be correlated to GNSS data todetermine locations corresponding to the stops. For example, the GNSSlocation information can be associated with a time. The motion sensordata can be associated with a time. The GNSS location information andthe motion sensor data can be correlated based on time to determine alocation and duration of a stop.

In some implementations, mobile device 102 can transmit or report thetraffic information to server 112 (e.g., navigation server) over network110 (e.g., the internet). For example, mobile device 102 can connect tonetwork 110 through cellular (or WiFi) transmitter (or wireless accesspoint) 108. In some implementations, the traffic information collectedfrom mobile device 102 (and collected from mobile device 104) can beused to determine traffic patterns associated with stop signs and stoplights as the mobile device moves on various roadways. For example,server 112 can collect traffic information from many mobile devices,correlate the traffic information based on location and time, forexample, and determine the locations and durations of stops at stopsigns and stop lights based on the traffic patterns observed in thecollected traffic information.

In some implementations, the traffic information can be reported toserver 112 in real-time or near real-time. In some implementations, thetraffic information can be stored on mobile device 102 and reported toserver 112 at a later time. For example, mobile device 102 may not beconnected to network 110 when the traffic information is collected.Thus, mobile device 102 can store the traffic information to an internalstorage device and report the traffic information to server 112 whenmobile device 102 later establishes a connection with network 110 (e.g.,when mobile device 102 later establishes a connection to a WiFi accesspoint).

In some implementations, server 112 can determine routes based on stopsign and/or stop light information. For example, once server 112 hasdetermined locations and delays associated with detected stop signsand/or stop lights, server 112 can use the location and delayinformation to suggest routes to users. For example, a user of mobiledevice 102 may request a route from a first location (e.g., Point A) toa second location (e.g., Point B). Typically, server 112 can determineone or more routes from Point A to Point B based on distance and/orduration (e.g., travel time). For example, a user can often indicate ina route request whether the user wants the shortest distance to thedestination or the quickest time to the destination. If the user wantsthe quickest time to the destination (e.g., shortest trip duration),then the server can estimate the travel time from Point A to Point B bymultiplying the distance between Point A and Point B by a known speedlimit or average speed for the roads connecting Point A and Point B.However, when surface streets (e.g., non-highway roads) are involved, atime estimate based only on distance and speed can be inaccurate due tostops (e.g., delays) necessitated by stop signs and stop lights. Thus,in some implementations, server 112 can identify locations of stop signsand/or stop lights, determine average lengths of time (e.g., delays) forstops at stop signs and stop lights, and include the delay timeattributed to stop signs and stop lights to the travel time estimate togenerate a more accurate trip time estimate.

In some implementations, once server 112 determines routes based on stopsign and stop light information, server 112 can transmit the determinedroutes and/or stop sign and stop light information to mobile device 102for presentation to the user.

Detecting Stop Signs

FIG. 2 is an illustration 200 of traffic patterns associated with a stopsign. For example, a mobile device (e.g., mobile device 102 or 104)carried within a vehicle can detect, record and/or report movement ofthe vehicle so that traffic patterns associated with a stop sign can bedetected and used for navigational purposes, as described herein. Forexample, illustration 200 depicts an intersection 202 having a stop sign204. As vehicles 206, 208 and/or 210 approach stop sign 204, eachvehicle will momentarily stop at the stop sign and then drive off, likevehicle 212. If there is more than one vehicle queued (e.g., vehicles206, 208 and 210) at stop sign 204, each vehicle will proceed in a stopand go fashion toward the stop sign. Once vehicles 206, 208 and 210 stopat the location of the stop sign, each vehicle will drive off, likevehicle 212. Thus, a stop sign can be characterized by a pattern ofmovement (e.g., traffic pattern) that includes stops of short durations(e.g., less than a threshold period of time) alternating with movementsof short distance (e.g., less than a threshold distance) and ending withmovement of a longer distance (e.g., greater than a threshold distance)and/or duration (e.g., greater than a threshold period of time).

In some implementations, stop sign approach thresholds and stop signdeparture thresholds can be used to determine a pattern of movement(e.g., traffic pattern) associated with a stop sign. For example, twoapproach thresholds can be defined for a stop sign pattern ofmovement: 1) the stop duration threshold and 2) the movement distancethreshold. These approach thresholds can be used to identify movement ofa mobile device in advance of the location of a stop sign. The stopduration threshold can be a short period of time (e.g., three seconds).The movement distance threshold can be a short distance (e.g., two carlengths). In some implementations, the stop duration threshold and themovement distance threshold can be used for identifying the stop-and-gomovement of a vehicle approaching a stop sign. Similarly, two departurethresholds can be defined for a stop sign pattern of movement: 1) thedrive off distance threshold and 2) the drive off duration threshold.These departure thresholds can be used independently or in combinationto determine when the mobile device has left the location of a stopsign. For example, the location of the stop sign can be identified asthe location of the last stop before the movement exceeding the driveoff distance threshold and/or the drive off duration threshold.

In some implementations, the location of stop sign 204 can be identifiedwhen mobile device 102 detects a single stop of a short duration (e.g.,stop duration threshold, 3 seconds) at a location and followed bymovement for more than a threshold duration (e.g., drive off durationthreshold, ten seconds) and/or more than a threshold distance (e.g.,drive off distance threshold, greater than fifty feet). For example, asingle car approaching a stop sign will stop briefly (e.g., less thanthe stop duration threshold) at the stop sign and then drive off. Thelocation of the single brief stop can be identified as a location of thestop sign.

In some implementations, the location of stop sign 204 can be identifiedwhen mobile device 102 detects two or more stops of a short duration(e.g., less than the stop duration threshold) where the stops are lessthan a threshold distance (e.g., less than the stop distance threshold)apart and followed by movement for more than a threshold duration (e.g.,drive off duration threshold) and/or more than a threshold distance(e.g., drive off distance threshold, greater than fifty feet). Forexample, the location of the stop sign can be identified as the locationof the last stop before the movement that exceeds the drive off durationthreshold and/or drive off distance threshold.

In some implementations, the accuracy of the stop sign locationdetermination can be improved by collecting and correlating trafficinformation from many mobile devices (e.g., mobile devices 102 and 104).For example, if the traffic patterns attributable to a stop sign at aparticular location are detected in traffic information received frommultiple mobile devices, then there is a high probability that a stopsign does in fact exist at the determined location. However, if just oneor two devices report traffic information that includes a stop signpattern of movement for a location, then the system can identify thepattern of movement as an anomaly attributable, perhaps, to an unusualroad condition, or unusual behavior of the driver of the vehicle.

Detecting Stop Lights

FIG. 3 is an illustration 300 of traffic patterns associated with a stoplight. For example, a mobile device (e.g., mobile device 102 or 104)carried within a vehicle can detect, record and/or report movement ofthe vehicle so that traffic patterns associated with a stop light can bedetected and used for navigational purposes, as described herein. Forexample, illustration 300 depicts an intersection 302 having a stoplight 304. As vehicles 306, 308 and/or 310 approach stop light 304, eachvehicle will stop at the stop light for the duration of the stop lightand then drive off (e.g., vehicle 312). If there is more than onevehicle queued (e.g., vehicles 306, 308 and/or 310) at stop light 304,each vehicle will wait until the stop light indicates that the vehiclescan proceed through intersection 302 (e.g., stop light turns green). Incontrast to a stop sign, vehicles queued at a stop light do not proceedin a stop and go fashion toward the stop light and through theintersection. Instead, vehicles queued at the stop light will stoptogether and then proceed together through the intersection as a grouponce the stop light indicates that the vehicles can proceed through theintersection. Thus, a stop light pattern of movement (e.g., trafficpattern) can be characterized as a single stop proximate to anintersection and exceeding a stop light duration threshold followed by amovement exceeding a stop light movement threshold through theintersection. For example, vehicle 306 may be queued at stop light 304but may not be at intersection 302 because vehicles 308 and 310 are infront of vehicle 306 but because vehicle 306 is queued near intersection302, vehicle 306 is considered to be proximate to intersection 302.

In some implementations, the location of stop light 304 can bedetermined based on traffic information received from multiple mobiledevices. For example, if vehicles 306, 308 and 310 are queued (e.g.,stopped) at a stop light, each vehicle will have a different locationassociated with the stop detected by the mobile device. The location ofthe stop of an individual vehicle (e.g., vehicle 306) may not indicatethe location of stop light 304. However, when the traffic informationreceived from mobile devices associated with vehicles 306, 308 and 310is correlated and analyzed as a whole, the server can determine that thelocation of the stop associated with vehicle 310 is the correct locationof stop light 304.

In some implementations, the location of the stop light can bedetermined based on the detected stop nearest an intersection. Forexample, if vehicles 306, 308 and 310 are stopped and queued at stoplight 304 (e.g., intersection 302), then the mobile device associatedwith each vehicle can report traffic information to the serverindicating the respective location where the vehicle is stopped.Additionally, the server can obtain map information indicating thelocations of highways, roads and intersections. For example, the mapinformation can be stored on the server or downloaded from a map server.The server can compare the vehicle stop locations to intersectionlocation information to determine vehicle stop locations that are nearintersection locations. The server can then identify the location of astop light to be the location of an intersection proximate (e.g., withina threshold distance, within one car length) to the vehicle stops.Alternatively, the server can identify the location of the stop light tobe the location of the vehicle stop nearest (e.g., within a thresholddistance) of an intersection location.

In some implementations, traffic patterns attributable to stop signsand/or stop lights can be detected based on a threshold number of mobiledevices reporting the stop sign and/or stop light traffic patterns. Forexample, when approaching a stop sign, some vehicles may make stops thatare longer than the above described stop sign approach thresholds. Whenapproaching a stop light, some vehicles may make stops that are lessthan the stop light duration threshold. However, when taken as a whole,most mobile devices may report stop durations and movement distancesthat are consistent with the stop sign/stop light traffic patterns,described above. Thus, in some implementations, a stop sign and/or stoplight traffic pattern can be detected when a threshold percentage (e.g.,greater than 60%) of mobile devices report traffic patterns consistentwith stop sign and/or stop light locations, as described above.

Detecting Problems with Stop Lights

In some implementations, stop light malfunctions can be determined basedon a stop sign traffic pattern. For example, a stop light location canbe determined as described above. When a stop light malfunctions, oftenthe traffic patterns approaching the malfunctioning stop light willappear to be a stop sign traffic pattern. Thus, in some implementations,when a stop sign traffic pattern is detected at a known stop lightlocation, a stop light malfunction can be detected.

Presenting Stop Information

In some implementations, the server can transmit stop sign and/or stoplight information to a mobile device for presentation on the display ofthe mobile device. For example, the server can collect trafficinformation from multiple devices, correlate and analyze the trafficinformation to identify traffic patterns attributable to stop signs andstop lights, as described above, and identify the locations of the stopsigns and stop lights based on the locations corresponding to theidentified traffic patterns. Additionally, the server can use thereported traffic information to determine how much time vehicles spendat a stop sign and/or stop light.

In some implementations, when a mobile device reports trafficinformation to the server, the server can determine how long it took thevehicle associated with the mobile device to get through (e.g., how longthe vehicle was delayed at) a stop sign. For example, when a stop signpattern of movement is detected in a mobile device's reported trafficinformation, the server can add up the duration of each stop associatedwith the stop sign to determine how much time is spent navigatingthrough the stop sign. The summation of the stop durations can be thedelay attributable to the stop sign.

In some implementations, when a mobile device reports trafficinformation to the server, the server can determine how long it took thevehicle associated with the mobile device to get through a stop light.For example, when a stop light pattern of movement is detected in amobile device's reported traffic information, the server can use theduration of the stop (or stops) at the stop light to determine the delayattributable to the stop light.

In some implementations, the delay attributable to a stop sign and/orstop light can be averaged. For example, the server can average thedelay across multiple vehicles (multiple mobile devices). The averagedelay for a stop sign/stop light can be the average of all vehicles, theaverage for a particular day of the week and/or the average for aparticular time of day. For example, the traffic information reported bya mobile device can be associated with a time of day when the movement,stop, location, traffic pattern, etc. was detected by the mobile device.The server can correlate traffic information across mobile devices basedon time of day to determine average delays attributable to a stopsign/stop light at a time of day. For example, a user can request toview stop sign/stop light information for a time of day (e.g., 5:00 pm)and the server can average the delays attributable for stop signs/stoplights within a window (e.g., +/−5 minutes, 4:55 pm-5:05 pm) thatincludes the requested time. The server can send the stop sign/stoplight information (e.g., in addition to other traffic information) tothe mobile device for presentation on a display of the mobile device.

FIG. 4 is an example graphical user interface 400 for presenting stopsign/stop light information. In some implementations, graphical userinterface 400 can present a map 402 of a geographic area. For example,the user can specify a location and the mobile device can present ageographic area that includes the location on graphical user interface400. The user can provide input (e.g., touch input) to scroll map 402 tocause different geographical areas to be presented in graphical userinterface 400, for example. In some implementations, the geographic areapresented on graphical interface 400 can correspond to a route requestedby the user. For example, the user can enter a start location and adestination location and the mobile device can present a maprepresenting a geographic area that includes the one or more routes. Theuser can then provide input requesting the mobile device to display stopsign/stop light information, as illustrated by FIG. 4.

In some implementations, graphical user interface 400 can presentlocations of stop signs and stop lights on map 402. For example,graphical objects 404-408 can represent locations of stop signs asdetermined by the stop sign traffic patterns described above withreference to FIG. 2. Graphical objects 410-412 can represent locationsof stop lights as determined by the stop light traffic patterns descriedabove with reference to FIG. 3. In some implementations, when the serverhas detected a problem with stop light 412, graphical object 414 can bedisplayed to indicate that stop light 412 is malfunctioning. A stoplight malfunction can be detected based on real-time traffic informationreported by mobile devices, as described above, for example. Once thereal-time traffic information (e.g., reported traffic patterns)indicates that the stop light is functioning normally again, graphicalobject 414 can be removed from the map display. In some implementations,a stop light malfunction can be indicated by modifying graphical object412 (e.g., the stop light icon). For example, instead of displayinggraphical object 414 (e.g., the warning icon), graphical object 412 canbe made to blink, flash or change color to indicate a problem with thecorresponding stop light.

In some implementations, graphical user interface 400 can presentgraphical objects 416 and 418 to present traffic information related tostop sign/stop light locations 404-412. For example, graphical objects416 and 418 can be lines having lengths and/or colors representingdelays attributable to stop sign 404 and stop light 412, respectively.In some implementations, a green, yellow, red color scheme can be usedto represent the amount of delay attributable to a stop sign or stoplight. Green can be displayed when the delay is less than a thresholdvalue (e.g., less than 30 seconds). Red can be displayed when the delayis greater than a threshold value (e.g., greater than five minutes).Yellow can be displayed when the delay is between the green and yellowthreshold values. In some implementations, the length or size ofgraphical objects 416 and 418 can represent the amount of delayattributable to a stop sign 404 or stop light 412. For example, thelonger (or larger) that graphical objects 416-418, the longer the delayattributable to the corresponding stop sign or stop light.

In some implementations, graphical user interface 400 can present stoplight and/or stop sign information for a user-selected time of day. Forexample, a user can specify a time of day (e.g., 9:00 AM on a Monday)and graphical user interface 400 can present graphical objects 416 and418 representing (e.g., average) stop sign/stop light information forthe specified time of day or a time period (e.g., window) including thespecified time of day.

In some implementations, graphical user interface 400 can presentinteractive graphical objects for specifying a time of day for whichstop sign/stop light information should be presented. In someimplementations, graphical user interface 400 can present graphicalobject 420 for specifying a day of the week. For example, graphicalobject 420 can be a pull down menu that lists the days of the week(e.g., Monday-Sunday) and/or a range of days (e.g., All, Weekdays,Weekends, etc.). For example, the user can select “Monday” to viewaverage stop sign/stop light information (e.g., durations, delays, etc.)for Mondays.

In some implementations, graphical user interface 400 can presentgraphical objects 422 and 424 for specifying a time of day for whichstop sign/stop light information should be presented. For example,graphical object 422 can be a slider bar and graphical object 424 can bethe slider handle. A user can select and drag graphical object 424 alonggraphical object 422 to adjust the time of day for which stop sign/stoplight information is presented. For example, the far left end ofgraphical object 422 can correspond to 12:00 AM, as represented ongraphical user interface 400 by graphical object 426. The far right endof graphical object 422 can correspond to 11:59 PM, as represented ongraphical user interface 400 by graphical object 428. The user canselect and drag graphical object 424 left and right along graphicalobject 422 to adjust the time of day between 12:00 AM and 11:59 PM. Forexample, the user can select and drag graphical object 424 so that thestop sign/stop light information corresponds to 11:00 AM, as representedon graphical user interface 400 by graphical object 430.

In some implementations, a user can view stop light/stop signinformation for a particular time of day of a particular day of theweek. For example, the user can interact with graphical object 420 toselect a day of the week or range of days and interact with graphicalobjects 422 and 424 to select a time of day. Thus, a user can view stopsign/stop light information for a particular time of a particular day ofthe week. Allowing the user to view stop sign/stop light information inthis manner can allow the user to plan ahead and choose a more efficienttime of day and/or route to travel.

Suggesting a Departure Time

FIG. 5 is an example user interface 500 for receiving routingparameters. For example, graphical user interface 500 can includegraphical objects 502 and 504 for specifying a start location (502) anda destination location (504) for a route. The start location and thedestination location can be transmitted to the server when the userselects graphical object 506. The server can determine routes betweenthe start location 502 and the destination location 504.

In some implementations, the server can determine routes based on delaysattributable to stop signs and/or stop lights along a route. Forexample, the server can determine the amount of time that it will taketo traverse various routes between start location 502 and destinationlocation 504 based on distance and speed. In some implementations, theserver can determine the amount of time it will take to traverse variousroutes between start location 502 and destination 504 based on collectedtraffic information. For example, when the mobile devices report trafficinformation (e.g., location, time, stops, etc.) to the server, theserver can use the location and time information in the trafficinformation to determine the average amount of time it takes to traversevarious routes or route segments between the start location and thedestination location. The server can add in the delays attributable tothe stop signs and/or stop lights along each route as determinedaccording to the techniques described above. The server can determinewhich route takes less time based on the distance, speed and stopsign/stop light delays for each route and prioritize the routes or makea route recommendation to the user according to which route takes lesstime.

In some implementations, the server can suggest a departure time basedon stop sign and/or stop light traffic information. For example, a usercan select continuous drive option 508 and enter an arrival time 510 fora destination 504 to have the server can suggest a departure time 512that will result in a trip with fewest or shortest stops. For example,the server can analyze traffic patterns associated with stop signsand/or stop lights to determine when (e.g., what time of day) stops(e.g., delays) at stop signs and/or stop lights are shortest. The servercan analyze the traffic patterns attributable to stop lights todetermine when (e.g., what time of day) stop lights turn green and allowtraffic through an intersection. The server can determine, based on theanalysis of the stop sign and stop light traffic patterns, a departuretime for a route between the start location 502 and the destinationlocation 504 that will result in the fewest or shortest stops. Forexample, the server can predict, based on departure time, distance,speed and stop sign/stop light delays, when the user will encounter eachstop sign and stop light along a route. The server can then suggest adeparture time so that the user encounters the shortest stops at stopsigns and stop lights and/or green lights at stop lights. For example,if the user departs the start location at the suggested departure time,the user may experience a continuous or near-continuous drive to thedestination location.

Example Processes

FIG. 6A is flow diagram of an example process 600 for stop sign/stoplight determination. At step 602, a server can receive trafficinformation from mobile devices. For example, traffic information can becrowd sourced from many mobile devices. The mobile devices can collecttraffic information (e.g., location, movement and time information), asdescribed above, and report the traffic information to the server foranalysis.

At step 604, the server can analyze the traffic information to identifystop sign and/or stop light traffic patterns. For example, the servercan analyze the traffic information for patterns of movementattributable to stop signs and stop lights, as described above withreference to FIGS. 2 and 3.

At step 606, the server can determine attributes of stop signs and stopsigns based on the traffic patterns. For example, the server candetermine, based on the identified stop sign/stop light trafficpatterns, the locations of stop signs and stop lights. The server candetermine delays attributable to stop signs and stop lights. The servercan determine schedules associated with stop signs and stop lights(e.g., amount of delay per time of day, when stop lights are green, whenstop lights are red).

At step 608, the server can transmit the stop sign/stop light attributeinformation to a mobile device. For example, the mobile device canrequest stop sign/stop light attribute information for a geographic areafrom the server and the server can transmit the stop sign/stop lightattribute information to the mobile device for presentation to a user.

FIG. 6B is a flow diagram of an example process 620 for displaying stopsign/stop light information. At step 622, user input to display stopsign/stop light attributes can be received by a mobile device. Forexample, a user viewing a map or navigation application on the mobiledevice can select an option to view stop sign and stop light attributesfor a geographic area.

At step 624, the geographic area can be transmitted to a server. Forexample, the server can collect and correlate traffic information, asdescribed above, and determine attributes (e.g., locations, delays,schedules, etc.) for stop signs and/or stop lights for the geographicarea.

At step 626, the mobile device can receive stop sign/stop lightattributes for the geographic area and current time. For example, theserver can determine stop sign/stop light attributes for the geographicarea and the current day and time. The server can transmit the stopsign/stop light attributes to the mobile device.

At step 628, the mobile device can display the stop sign/stop lightattributes for the geographic area and current time. For example, themobile device can display the stop sign/stop light attributes asdescribed above with reference to FIG. 4.

At step 630, the mobile device can receive input specifying a day and/ortime of day. For example, the mobile device can receive user inputspecifying a day and/or time of day as described above with reference toFIG. 4.

At step 632, the mobile device can transmit the user-specified dayand/or time of day to the server. For example, the server can determinestop sign/stop light attributes for the user specified day and time ofday and transmit the stop sign/stop light attributes to the mobiledevice for presentation to the user. Thus, the mobile device can receivethe stop sign/stop light attributes for the geographic area and the userspecified time of day, at step 634.

At step 636, the mobile device can display the stop sign/stop lightattributes for the geographic area and the specified day and time ofday. For example, the mobile device can display the stop sign/stop lightattributes as described above with reference to FIG. 4.

In some implementations, the server can transmit stop sign/stop lightattributes information for many geographic areas and for many days andtimes of day. For example, the server can transmit stop sign/stop lightattribute information to the mobile device for the current geographiclocation of the mobile device and the geographic locations surroundingthe current geographic location of the mobile device. The server cantransmit stop sign/stop light attribute information for all days and alltimes of day. The mobile device can store the stop sign/stop lightattribute information and determine stop sign/stop light information fora geographic area and time of day based on the stored informationwithout having to request the information from the server when a userprovides new geographic area, day and/or time of day input.

In some implementations, the mobile device can periodically requestupdated stop sign/stop light information. For example, the mobile devicecan request stop light/stop sign attribute information from the serveronce a month, every other month, or every six months.

In some implementations, the server can push new stop sign/stop lightattribute information to the mobile device when a real-time update isrequired. For example, when the server detects a stop light malfunction,the server can push the stop light malfunction information to the mobiledevice so that the mobile device can present the stop light malfunctionto the user, as described above with reference to FIG. 4.

FIG. 6C is a flow diagram of an example process 650 for routedetermination based on stop sign/stop light information. At step 652, astart location and a destination location can be received. For example,the mobile device can receive user input specifying a start location anda destination location for a route. The start location can be thecurrent location of the mobile device. The current location can beautomatically determined by the mobile device. In some implementations,a server can perform the route determination. For example, if a serveris performing the route determination, the start location anddestination location can be transmitted to the server. In someimplementations, a mobile device can perform the route determination.For example, if the mobile device is performing the route determination,the server can transmit the navigation information necessary forperforming the route determination, including the stop sign/stop lightattribute information, to the mobile device, as described above. Themobile device can store the navigation information and use thenavigation information to perform the route determination according tothe following steps.

At step 654, routes between the start location and the destinationlocation can be determined. For example, the server or mobile device candetermine the three or four shortest routes between the start locationand destination location. The server or mobile device can determine thethree or four fastest routes between the start location and thedestination location based on travel times calculated based on distanceand road speed.

At step 656, stop signs and/or stop lights along the determined routescan be identified. For example, the server or mobile device can use thestop sign/stop light attributes determined according to process 600 toidentify stop signs and/or stop lights located along the determinedroutes.

At step 658, delays attributable to stop signs and/or stop lights alongthe determined routes can be determined. For example, the server ormobile device can use the stop sign/stop light attributes determinedaccording to process 600 to determine the delays attributable to stopsigns and/or stop lights located along the determined routes.

At step 660, the travel times for routes based on the stop sign and/orstop light delays can be determined. For example, the server or mobiledevice can add the delays attributable to the stop signs and/or stoplights along the determined routes to the travel times calculated basedon distance and speed for each route to determine which route has theshortest travel times.

At step 662, the routes determined based on stop sign/stop lightinformation can be presented on the mobile device. For example, if theserver determined the routes, the server can transmit the routes to themobile device. The mobile device can present the routes according tofewest stops, shortest trip time or shortest distance, for example.

Example System Architecture

FIG. 7 is a block diagram of an example computing device 700 that canimplement the features and processes of FIGS. 1-6C. The computing device700 can include a memory interface 702, one or more data processors,image processors and/or central processing units 704, and a peripheralsinterface 706. The memory interface 702, the one or more processors 704and/or the peripherals interface 706 can be separate components or canbe integrated in one or more integrated circuits. The various componentsin the computing device 700 can be coupled by one or more communicationbuses or signal lines.

Sensors, devices, and subsystems can be coupled to the peripheralsinterface 706 to facilitate multiple functionalities. For example, amotion sensor 710, a light sensor 712, and a proximity sensor 714 can becoupled to the peripherals interface 706 to facilitate orientation,lighting, and proximity functions. Other sensors 716 can also beconnected to the peripherals interface 706, such as a global navigationsatellite system (GNSS) (e.g., GPS receiver), a temperature sensor, abiometric sensor, or other sensing device, to facilitate relatedfunctionalities.

A camera subsystem 720 and an optical sensor 722, e.g., a chargedcoupled device (CCD) or a complementary metal-oxide semiconductor (CMOS)optical sensor, can be utilized to facilitate camera functions, such asrecording photographs and video clips.

Communication functions can be facilitated through one or more wirelesscommunication subsystems 724, which can include radio frequencyreceivers and transmitters and/or optical (e.g., infrared) receivers andtransmitters. The specific design and implementation of thecommunication subsystem 724 can depend on the communication network(s)over which the computing device 700 is intended to operate. For example,the computing device 700 can include communication subsystems 724designed to operate over a GSM network, a GPRS network, an EDGE network,a Wi-Fi or WiMax network, and a Bluetooth™ network. In particular, thewireless communication subsystems 724 can include hosting protocols suchthat the computing device 700 can be configured as a base station forother wireless devices.

An audio subsystem 726 can be coupled to a speaker 728 and a microphone730 to facilitate voice-enabled functions, such as speaker recognition,voice replication, digital recording, and telephony functions. The audiosubsystem 726 can be configured to facilitate processing voice commands,voiceprinting and voice authentication.

The I/O subsystem 740 can include a touch-surface controller 742 and/orother input controller(s) 744. The touch-surface controller 742 can becoupled to a touch surface 746. The touch surface 746 and touch-surfacecontroller 742 can, for example, detect contact and movement or breakthereof using any of a plurality of touch sensitivity technologies,including but not limited to capacitive, resistive, infrared, andsurface acoustic wave technologies, as well as other proximity sensorarrays or other elements for determining one or more points of contactwith the touch surface 746.

The other input controller(s) 744 can be coupled to other input/controldevices 748, such as one or more buttons, rocker switches, thumb-wheel,infrared port, USB port, and/or a pointer device such as a stylus. Theone or more buttons (not shown) can include an up/down button for volumecontrol of the speaker 728 and/or the microphone 730.

In one implementation, a pressing of the button for a first duration candisengage a lock of the touch surface 746; and a pressing of the buttonfor a second duration that is longer than the first duration can turnpower to the computing device 700 on or off. Pressing the button for athird duration can activate a voice control, or voice command, modulethat enables the user to speak commands into the microphone 730 to causethe device to execute the spoken command. The user can customize afunctionality of one or more of the buttons. The touch surface 746 can,for example, also be used to implement virtual or soft buttons and/or akeyboard.

In some implementations, the computing device 700 can present recordedaudio and/or video files, such as MP3, AAC, and MPEG files. In someimplementations, the computing device 700 can include the functionalityof an MP3 player, such as an iPod™. The computing device 700 can,therefore, include a 36-pin connector that is compatible with the iPod.Other input/output and control devices can also be used.

The memory interface 702 can be coupled to memory 750. The memory 750can include high-speed random access memory and/or non-volatile memory,such as one or more magnetic disk storage devices, one or more opticalstorage devices, and/or flash memory (e.g., NAND, NOR). The memory 750can store an operating system 752, such as Darwin, RTXC, LINUX, UNIX, OSX, WINDOWS, or an embedded operating system such as VxWorks.

The operating system 752 can include instructions for handling basicsystem services and for performing hardware dependent tasks. In someimplementations, the operating system 752 can be a kernel (e.g., UNIXkernel). In some implementations, the operating system 752 can includeinstructions for performing voice authentication. For example, operatingsystem 752 can implement the location tracking features as describedwith reference to FIGS. 1-6C.

The memory 750 can also store communication instructions 754 tofacilitate communicating with one or more additional devices, one ormore computers and/or one or more servers. The memory 750 can includegraphical user interface instructions 756 to facilitate graphic userinterface processing; sensor processing instructions 758 to facilitatesensor-related processing and functions; phone instructions 760 tofacilitate phone-related processes and functions; electronic messaginginstructions 762 to facilitate electronic-messaging related processesand functions; web browsing instructions 764 to facilitate webbrowsing-related processes and functions; media processing instructions766 to facilitate media processing-related processes and functions;GNSS/Navigation instructions 768 to facilitate GNSS andnavigation-related processes and instructions; and/or camerainstructions 770 to facilitate camera-related processes and functions.The memory 750 can store navigation and/or routing software instructions772 to facilitate the location tracking, navigation and routingprocesses and functions described with reference to FIGS. 1-6C.

The memory 750 can also store other software instructions 774, such asweb video instructions to facilitate web video-related processes andfunctions; and/or web shopping instructions to facilitate webshopping-related processes and functions. In some implementations, themedia processing instructions 766 are divided into audio processinginstructions and video processing instructions to facilitate audioprocessing-related processes and functions and video processing-relatedprocesses and functions, respectively.

Each of the above identified instructions and applications cancorrespond to a set of instructions for performing one or more functionsdescribed above. These instructions need not be implemented as separatesoftware programs, procedures, or modules. The memory 750 can includeadditional instructions or fewer instructions. Furthermore, variousfunctions of the computing device 700 can be implemented in hardwareand/or in software, including in one or more signal processing and/orapplication specific integrated circuits.

What is claimed is:
 1. A method comprising: receiving, at a serverdevice, traffic information from a plurality of mobile devices, thetraffic information including stop duration information, movementduration information, and distance information; generating analyzedtraffic information by comparing, by the server device, the stopduration information, movement duration information, and distanceinformation to corresponding thresholds, the corresponding thresholdsassociated with a traffic pattern attributable to stop signs or stoplights; and determining by the server device, based on the analyzedtraffic information, locations of stop signs or stop lights.
 2. Themethod of claim 1, further comprising: determining, based on theanalyzed traffic information, delays attributable to stop signs or stoplights.
 3. The method of claim 2, further comprising: receiving a startlocation and a destination location; and determining a route between thestart location and the destination location based on the delaysattributable to stop signs or stop lights along the route.
 4. The methodof claim 2, further comprising: transmitting the locations and delaysassociated with the stop signs or stop lights to a mobile device, wherethe mobile device is configured to present the locations and delaysassociated with the stop signs or stop lights to a user of the mobiledevice.
 5. The method of claim 2, further comprising: receiving, from amobile device, at least one of a time of day and a day of the weekselected by a user of the mobile device; and determining delaysattributable to stop signs or stop lights and corresponding to theselected at least one of time of day and day of the week.
 6. A systemcomprising: one or more processors; and a computer-readable mediumincluding one or more sequences of instructions which, when executed byone or more processors, causes: receiving, at a server device, trafficinformation from a plurality of mobile devices, the traffic informationincluding stop duration information, movement duration information, anddistance information; generating analyzed traffic information bycomparing, by the server device, the stop duration information, movementduration information, and distance information to correspondingthresholds, the corresponding thresholds associated with a trafficpattern attributable to stop signs or stop lights; and determining bythe server device, based on the analyzed traffic information, locationsof stop signs or stop lights.
 7. The method of claim 2, furthercomprising: receiving, from a mobile device, a geographic area selectedby a user of the mobile device; and determining delays attributable tostop signs or stop lights within the selected geographic area.
 8. Themethod of claim 1, wherein the corresponding thresholds include one ormore stop duration thresholds, movement duration thresholds, anddeparture thresholds, wherein the thresholds, when met, are indicativeof either a traffic pattern associated with a stop sign or a trafficpattern indicative of a stop light.
 9. A non-transitorycomputer-readable medium including one or more sequences of instructionswhich, when executed by one or more processors, causes: receiving, at aserver device, traffic information from a plurality of mobile devices,the traffic information including stop duration information, movementduration information, and distance information; generating analyzedtraffic information by comparing, by the server device, the stopduration information, movement duration information, and distanceinformation to corresponding thresholds, the corresponding thresholdsassociated with a traffic pattern attributable to stop signs or stoplights; and determining by the server device, based on the analyzedtraffic information, locations of stop signs or stop lights.
 10. Thenon-transitory computer-readable medium of claim 9, wherein theinstructions cause: determining, based on the analyzed trafficinformation, delays attributable to stop signs or stop lights.
 11. Thenon-transitory computer-readable medium of claim 10, wherein theinstructions cause: receiving a start location and a destinationlocation; and determining a route between the start location and thedestination location based on the delays attributable to stop signs orstop lights along the route.
 12. The non-transitory computer-readablemedium of claim 10, wherein the instructions cause: transmitting thelocations and delays associated with the stop signs or stop lights to amobile device, where the mobile device is configured to present thelocations and delays associated with the stop signs or stop lights to auser of the mobile device.
 13. The non-transitory computer-readablemedium of claim 10, wherein the instructions cause: receiving, from amobile device, at least one of a time of day and a day of the weekselected by a user of the mobile device; and determining delaysattributable to stop signs or stop lights and corresponding to theselected at least one of a time of day and day of the week.
 14. Thenon-transitory computer-readable medium of claim 10, wherein theinstructions cause: receiving, from a mobile device, a geographic areaselected by a user of the mobile device; and determining delaysattributable to stop signs or stop lights within the selected geographicarea.
 15. The non-transitory computer-readable medium of claim 9,wherein the corresponding thresholds include one or more stop durationthresholds, movement duration thresholds, and departure thresholds,wherein the thresholds, when met, are indicative of either a trafficpattern associated with a stop sign or a traffic pattern indicative of astop light.
 16. The system of claim 6, wherein the correspondingthresholds include one or more stop duration thresholds, movementduration thresholds, and departure thresholds, wherein the thresholds,when met, are indicative of either a traffic pattern associated with astop sign or a traffic pattern indicative of a stop light.
 17. Thesystem of claim 16, wherein the instructions cause: determining, basedon the analyzed traffic information, delays attributable to stop signsor stop lights.
 18. The system of claim 17, wherein the instructionscause: receiving a start location and a destination location; anddetermining a route between the start location and the destinationlocation based on the delays attributable to stop signs or stop lightsalong the route.
 19. The system of claim 17, wherein the instructionscause: transmitting the locations and delays associated with the stopsigns or stop lights to a mobile device, where the mobile device isconfigured to present the locations and delays associated with the stopsigns or stop lights to a user of the mobile device.
 20. The system ofclaim 17, wherein the instructions cause: receiving, from a mobiledevice, at least one of a time of day and a day of the week selected bya user of the mobile device; and determining delays attributable to stopsigns or stop lights and corresponding to the selected at least one of atime of day and day of the week.
 21. The system of claim 17, wherein theinstructions cause: receiving, from a mobile device, a geographic areaselected by a user of the mobile device; and determining delaysattributable to stop signs or stop lights within the selected geographicarea.